Refactor limayaml.Save and store.SaveYAML → limayaml.Marshal #2726
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
store.SaveYAML
was the only caller oflimayaml.Save
, and was only called frommain.validateAction
.The name
Save
implies writing to a file, soMarshal
seems like a more logical choice for the name. And since it is marshallinglimayaml
structs it should be in thelimayaml
package and not instore
.Also move
limayaml.unmarshalYAML
fromload.go
tomarshal.go
for consistency.I was wondering if
load.go
andmarshal.go
should be combined into a single file, but kept them separate for now.I also feel like
store.LoadYAMLByFilePath
should probably belong in thelimayaml
package, but am not sure.